-
Notifications
You must be signed in to change notification settings - Fork 380
Update google.golang.org/grpc #594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Update google.golang.org/grpc #594
Conversation
84cc41c
to
778d00d
Compare
778d00d
to
a2d34c2
Compare
|
||
require ( | ||
google.golang.org/grpc v1.57.1 | ||
google.golang.org/protobuf v1.33.0 | ||
github.com/golang/protobuf v1.5.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How did this deprecated link become a direct reference? It should be an indirect one used by google.golang.org/protobuf internally.
golang.org/x/net v0.38.0 // indirect | ||
golang.org/x/sys v0.31.0 // indirect | ||
golang.org/x/text v0.23.0 // indirect | ||
google.golang.org/genproto/googleapis/rpc v0.0.0-20250324211829-b45e905df463 // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm getting this without generated files under lib/go/csi:
module github.com/container-storage-interface/spec
go 1.23.0
toolchain go1.24.4
require (
google.golang.org/grpc v1.73.0
google.golang.org/protobuf v1.36.6
)
require (
golang.org/x/net v0.38.0 // indirect
golang.org/x/sys v0.31.0 // indirect
golang.org/x/text v0.23.0 // indirect
google.golang.org/genproto/googleapis/rpc v0.0.0-20250324211829-b45e905df463 // indirect
)
/close |
/close Resolved by upgrading github.com/golang/protobuf v1.5.4 |
/close |
What type of PR is this?
Update google.golang.org/grpc
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce an API-breaking change?: